I don't love the cards there because it goes against the flow that the "next"-buttons try to suggest. A sentence with links to the steps is less confusing I think because there's fewer boxes.

I have an alternate suggestion, why don't we do:

1. Capture and annotate images
2. Create a training dataset (which includes adding to a training dataset)

capture and annotate could be separate but I feel like that might make create a training set less awkward?

This is still very odd to me. Like it essentially does both capture + annotate (which is the next page) and adding to dataset when we've split those across three pages. Either they're together and we have them in one page or this doesn't make sense

this snippet was inspired by the wine-pouring demo example linked to me as a good pattern, so i wanted to find a place for it. if you feel it doesn't fit into the flow of the pages as-is, would you rather i:

• removed this example entirely?
• rearranged the pages, perhaps combining add and annotate?

Reorganized according to your other comment; hopefully that helps!

yep this lgtm. I think keeping is good thought maintenance will be painful so future us might disagree

noting to self that we can significantly simplify this code when uploadfiletodataset happens

an image here might be great and more immediatly convey this but that doesn't need to necessarily happen with this PR

I'll brainstorm some ideas for this and submit a request

this is confusing. Because it's sort of begs the question - so if I do have a model, what then? So it should link to that code. which maybe means that this should go to the annotate page: https://deploy-preview-4413--viam-docs.netlify.app/data-ai/train/update-dataset/#capture-annotate-and-add-images-to-a-dataset

I think I misunderstand you, isn't this already on the annotate page? I put this admonition here to help guide people into the appropriate tab in the tabset that follows. Where are you thinking we could link?

Regardless I reworded this away from the question-begging 'unless', but me know if I'm missing something else.

Right now there is still capture and add to dataset content on two different pages which feels confusing.
It's hard to force a linear flow here since with all the different options for each step, the same order doesn't always apply:

• In most cases, like using the mobile app, uploading a batch, or adding existing images, you can get the data first and then create a dataset and add the data to it. Order doesn't matter, but it's easiest conceptually to think of getting data and then making a dataset with it.
• One exception: If you capture individual images through the UI and add them to a dataset on the spot, you have to have a dataset to add them to before you start capturing.
• In the script version of that same "Capture individual images" heading, it looks like you don't specify a dataset id, so you'd still have to add to a dataset later like with the other methods.

Suggestion:

• Implement Naomi's order suggestion, and:
• Get rid of the exception: Ask eng to change that capture button to not save to dataset but rather just save the image to your captured data. Just one single click, so you can capture more images in rapid succession, then add a batch all at once later. This would be a less clunky UX IMO, and also solve a docs flow problem.
  • If this will take a while but they'll do it, don't worry about this flow for now; document the rest per Naomi's order
• If this can't/won't ever be changed in eng, document this as a thing you can do but shape the docs around the normal capture-then-make-a-dataset order